Skip to content

chore(ci): bump actions to Node 24 versions#1592

Merged
yury-s merged 4 commits intomicrosoft:mainfrom
yury-s:chore-bump-actions-node24
May 1, 2026
Merged

chore(ci): bump actions to Node 24 versions#1592
yury-s merged 4 commits intomicrosoft:mainfrom
yury-s:chore-bump-actions-node24

Conversation

@yury-s
Copy link
Copy Markdown
Member

@yury-s yury-s commented May 1, 2026

Summary

  • Bump JavaScript actions to majors that ship using: node24, so the runtime moves off Node 20.
  • Bump CI node-version from 20 to 22 (Node 20 reached end-of-life in April 2026).
  • GitHub is forcing JavaScript actions to Node 24 by default on 2026-06-02 and removing Node 20 from runners on 2026-09-16.

Action bumps:

  • actions/checkout@v4@v5
  • actions/setup-node@v4@v5
  • docker/setup-qemu-action@v3@v4
  • docker/setup-buildx-action@v3@v4
  • docker/build-push-action@v6@v7
  • azure/login@v2@v3
  • oras-project/setup-oras@v1@v2

yury-s added 3 commits May 1, 2026 15:00
GitHub is forcing JavaScript actions to Node 24 by default on
2026-06-02 and removing Node 20 from runners on 2026-09-16.
Also bumps CI Node.js from 20 (EOL April 2026) to 22.

- actions/checkout@v4 -> v5
- actions/setup-node@v4 -> v5
- docker/setup-qemu-action@v3 -> v4
- docker/setup-buildx-action@v3 -> v4
- docker/build-push-action@v6 -> v7
- azure/login@v2 -> v3
- oras-project/setup-oras@v1 -> v2
- node-version 20 -> 22
Node 24 ships npm 11.12.1, which already satisfies the npm 11.5.1+
requirement for OIDC npm publishing.
Use the oldest supported LTS in CI to catch any reliance on
newer-Node-only behavior. Publish job stays on 24 for the
bundled npm 11.
Users may still be on Node.js 20 even after April 2026 EOL,
so keep CI testing on the oldest version we want to support.
The action runtime itself runs on Node 24 via setup-node@v5.
@yury-s yury-s merged commit d3c528d into microsoft:main May 1, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants